Improve pre-commit setup#297
Merged
meshy merged 5 commits intoclassy-python:mainfrom Apr 27, 2026
Merged
Conversation
Merged
Already enabled as a ruff rule set Relates to classy-python#236
ulgens
force-pushed
the
improve-pre-commit-setup
branch
from
59f2935 to
296c8a4
Compare
Contributor
Author
|
@meshy 👋🏻 How do you feel about this PR? I can separate it into multiple PRs, and/or add automated update mechanisms, and/or apply the changes you see fit. |
Contributor
|
This is very helpful, thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was checking the repository to add Django 6.0 to the docs, but realized there is room for improvement with pre-commit hooks.
Details can be found in individual commits.